Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines which are not met ❌

• I was not able to load the package (i.e. import IceFloeTracker failed). See the AutoMerge logs for details.

2. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

All but the AutoMerge action pass due to use of Python 3.12 by the CI which is not compatible with the versions of our Python deps. Is there a way to change that to Python 3.11? If not, please merge manually. Thanks!

The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: ImageBinarization, TiledIteration

This has to be fixed by you

[noblock]

The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: ImageBinarization, TiledIteration

This has to be fixed by you

[noblock]

@lgoettgens That has been fixed. They werent listed in the compat section before but now they are. Please see
https://github.com/WilhelmusLab/IceFloeTracker.jl/blob/ede819aa48550e70484cf45c56dd6fa2cbb5b66d/Project.toml#L71
https://github.com/WilhelmusLab/IceFloeTracker.jl/blob/ede819aa48550e70484cf45c56dd6fa2cbb5b66d/Project.toml#L97

Do they need something like "<2"? The other ones don't seem to need that.

"0" isn't a valid compat string. See the pkg.jl documentation for details. But basically, you have to list all 0.x versions that you are compatible with (since all of these are considered pair wise breaking)

[noblock]

[noblock]

Tip: https://github.com/GunnarFarneback/PackageCompatUI.jl can help you set your compat.

Tip: https://github.com/GunnarFarneback/PackageCompatUI.jl can help you set your compat.

@GunnarFarneback @lgoettgens
I think this is good now. Could you please take another look? Thanks for the guidance!

[noblock]

a lot of comments above are missing the [noblock] tag

And of course there is still the problem with loading the package